Is this copied from upstream wiseconnect files, or it's a modification to them? If it's copied, then it'd be good to mention exactly which version. If it's a modification, then we might want something similar to what we do with additional patches to SiSDK:https://github.com/zephyrproject-rtos/hal_silabs/blob/main/scripts/patch_simplicity_sdk.sh

Is this copied from upstream wiseconnect files, or it's a modification to them?

It is a modification. The upstream may be changed to avoid this patch, but it can't be applied as-is. That's said, maybe we could consider the adoption of the Upstream-Status: trailer.

[...] something similar to what we do with additional patches to SiSDK

For wiseconnect, we have a stack of patches to apply. So we cherry-pick all the patches each time we update wiseconnect. Automation of this task is on my TODO list.

@ArunmaniAlagarsamy2710, if you want to write a great commit log, try to explain why you think this patch should be applied:

Zephyr CMSIS implementation has some limitations with dynamically allocated
resources[1].

This patch allocates the CMSIS resources statically. Thus:
  - this allows to workaround the limitation of the current CMSIS implementation
    until we fix them properly
  - it is possible to get rid of the dependencies to
    CMSIS_V2_THREAD_DYNAMIC_MAX_COUNT and CMSIS_V2_THREAD_MAX_COUNT.

[1]: https://github.com/zephyrproject-rtos/zephyr/pull/85557

One last thing: we start to have (too) many patches applied on top of wiseconnect. I would like we start to use Upstream-status: trailer. If the patch will never be applied on upstream, add Upstream-status: inappropriate (explanation). (alternately, you can use the status pending, submitted or available)